cherry-pick: ContainerRegistry: Reject invalid repository names #141
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Cherry pick of #138.
ImageReferencedoes not check for illegal characters in parsed image references. This means thatcontainertoolwill send illegal image names to the registry. The registry will reject them, but the error message might not explain why, so a generic error message will be printed. Runtimes reject illegal image references immediately, without sending them to the registry.Modifications
Repositorywrapper typeRepositoryRepositoryinstead ofString.Result
It is impossible to create a
Repositoryobject containing a malformed name, because the constructor checks the string value. It is impossible to send a malformed name to the registry because the API wrappers only acceptRepositoryobjects.Fixes #135
Test Plan
Existing tests continue to pass.
New tests exercise additional checks which were previously missing.